You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.30 client can communicate with v1.29, v1.30, and v1.31 control planes. Using the latest compatible version of kubectl helps avoid unforeseen issues.

The following methods exist for installing kubectl on Windows:

Download the latest 1.30 patch release: kubectl 1.30.0.

Or if you have curl installed, use this command:

Validate the binary (optional)

Download the kubectl checksum file:

Validate the kubectl binary against the checksum file:

Using Command Prompt to manually compare CertUtil's output to the checksum file downloaded:

Using PowerShell to automate the verification using the -eq operator to get a True or False result:

Append or prepend the kubectl binary folder to your PATH environment variable.

Test to ensure the version of kubectl is the same as downloaded:

Or use this for detailed view of version:

To install kubectl on Windows you can use either Chocolatey package manager, Scoop command-line installer, or winget package manager.

Test to ensure the version you installed is up-to-date:

Navigate to your home directory:

Create the .kube directory:

Change to the .kube directory you just created:

Configure kubectl to use a remote Kubernetes cluster:

In order for kubectl to find and access a Kubernetes cluster, it needs a kubeconfig file, which is created automatically when you create a cluster using kube-up.sh or successfully deploy a Minikube cluster. By default, kubectl configuration is located at ~/.kube/config.

Check that kubectl is properly configured by getting the cluster state:

If you see a URL response, kubectl is correctly configured to access your cluster.

If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster.

For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above.

If kubectl cluster-info returns the url response but you can't access your cluster, to check whether it is configured properly, use:

In Kubernetes 1.26, kubectl removed the built-in authentication for the following cloud providers' managed Kubernetes offerings. These providers have released kubectl plugins to provide the cloud-specific authentication. For instructions, refer to the following provider documentation:

(There could also be other reasons to see the same error message, unrelated to that change.)

kubectl provides autocompletion support for Bash, Zsh, Fish, and PowerShell, which can save you a lot of typing.

Below are the procedures to set up autocompletion for PowerShell.

The kubectl completion script for PowerShell can be generated with the command kubectl completion powershell.

To do so in all your shell sessions, add the following line to your $PROFILE file:

This command will regenerate the auto-completion script on every PowerShell start up. You can also add the generated script directly to your $PROFILE file.

To add the generated script to your $PROFILE file, run the following line in your powershell prompt:

After reloading your shell, kubectl autocompletion should be working.

A plugin for Kubernetes command-line tool kubectl, which allows you to convert manifests between different API versions. This can be particularly helpful to migrate manifests to a non-deprecated api version with newer Kubernetes release. For more info, visit migrate to non deprecated apis

Download the latest release with the command:

Validate the binary (optional).

Download the kubectl-convert checksum file:

Validate the kubectl-convert binary against the checksum file:

Using Command Prompt to manually compare CertUtil's output to the checksum file downloaded:

Using PowerShell to automate the verification using the -eq operator to get a True or False result:

Append or prepend the kubectl-convert binary folder to your PATH environment variable.

Verify the plugin is successfully installed.

If you do not see an error, it means the plugin is successfully installed.

After installing the plugin, clean up the installation files:

Was this page helpful?

Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub Repository if you want to report a problem or suggest an improvement.